Tootfinder

After 124.1 hours and 4 achievements that were slightly bugged, I have finally 100% completed Enshrouded.
This game was super fun with lots of stuff to do and still things to do with regards to collecting armor, weapons and building my house/base.
I can't wait for a DLC or updated content, which is already being worked on by Keen Games. I highly recommend this game!
#Enshrouded

I'll be honest: I deeply admire some of you who have energy and motivation to participate in various "100 days to offload", "52 books", "national writing months" and other similar actions.
As soon as I attach an arbitrary metric to stuff I enjoy doing, it stops being fun and affects quality of what I do.
Sure, it's fun to measure things _afterwards_, but planning ahead with numbers in mind is something none of you want me to do if you enjoy w…

I am doing more complex than "connect this form to that database" work, but the core point I want to make here is that getting those things right keeps software from being slow. We can sweat the details and that's what lets our software deal with 10000 entries where we might normally only use 100 — but there's always That One User. A power user. A user who will recommend the software to their whole organization.
It means that we spend a lot less time asking "Why the !@#!@#!@# is it slow?" when someone does something bigger than we expect.
We do a lot less middle of the night debugging because we take the time to do things well and understand them down to both the metal and the algorithms.
Good computer engineering lets you actually take the time to understand things both theoretically and in the implementation.

💯 but don't forget they also solve problems you won't have for 100 lifetimes while making the things you actually want to do today more difficult
https://social.polotek.net/@polotek/112157268627081113

Marco Rogers (@polotek@social.polotek.net)
Attached: 1 image A thesis.

So uhm, I blogged. And to be honest, only to a small extent it is about photography.
#blog

I don't understand but I keep trying
Sometimes, however, I see things, I think I understand them... but when I’m out to do them on my own, it turns out I don’t.

what is the typical design process for multiple token buckets?
e.g. if you have a bunch of go routines that:
listen to new domain registrations ->
check for IP token bucket (or rough /30 bucket?) -> if rate limited, stack in list of things to do in that prefix?? send to disk?
check for ASN token bucket - if cidr range is unknown, send to ASN querying and sleep(?)
ASN querying go routine -> rate limited to a request every 8 hours (100/month), or every 2-ish hours (500/month) - cached once known
when ASN becomes unblocked -> /now/ you can query the domain
(this also applies to queue design in general, when the thing you're queuing for might take a long while to dequeue in breadth first search, or if you have multiple rate limits to respect)
e.g., if I have it run an insert into "asn_lookups_resume_domains" for the ASN job to lookup, then resume/retry the domain jobs
or if it's completely blocking
or if it's just n-workers such that probably some prefixes are unblocked

Time to hop on some more Fallout 76! I have 11 more expeditions to do until I can get my Union Power Armor Jet Packk mod....😬 I hate those damn things so I've only been doing 1-2 a day for a few days.
Sitting at 100 stamps and it costs 300...😫
#Fallout #Fallout76

I do dev posts from time to time for various reasons (usually I just want to archive things I've spent hours figuring out), but that article resonates with me a lot.
My inner self-critic can be annoyingly vocal at times.
https://manuelmoreale.com/why-i-don-t-write-…